Identification verification and authentication system

ABSTRACT

A system for verifying an identity of a user includes a first client electronic device associated with a first user, and a computer-readable storage medium having one or more programming instructions that, when executed, cause the first client electronic device to receive a first secret and a second secret, detect, a wireless signal being broadcast by a second client electronic device in proximity to a specified physical location where the interaction is to occur, establish a communication channel with the second client electronic device, send the first secret to the second client electronic device via the communication channel, receive data from the second client electronic device via the communication channel, determine whether the received data matches the second secret, and in response to determining that the received data matches the second secret, cause an alert to be provided to the first user via the first client electronic device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/247,492 filed Dec. 14, 2020, which is a continuation of U.S. patentapplication Ser. No. 16/862,690 filed Apr. 30, 2020, which claimspriority to U.S. Provisional Patent Appl. No. 62/841,492 filed May 1,2019, the disclosures of all of which are hereby incorporated byreference in their entireties.

BACKGROUND

Increasingly, today's world is moving to an on-demand or gig economy. Aspart of this transition, it is becoming normal for strangers to arrangeto meet at a specific time and place for a common purpose ortransaction. For example, strangers may arrange to meet for a date orother social interaction, to make a delivery, for ride services and/orthe like. Software applications have made arranging such meetings quickand easy.

However, despite the commonality, the element of stranger danger isstill present in these interactions. The companies providing theplatforms that play match-maker for these parties do their best to vetthe people that are providing these services, but inevitably some badactors will slip through the cracks. Also, some of these contractors ofthe platform company might permit non-vetted parties to perform in theirplace. For instance, a ride-share driver may lend out his or her vehicleto a non-vetted party unbeknownst to riders or the service making thematch. Even more concerning is the expectation that putting a logo on acar or clothes may easily trick an unsuspecting user into interactingwith someone who was never vetted in the first place.

While some services provide information pertaining to one or moreparties before the meeting, such as a picture, a name or a licenseplate, this information is sometimes not sufficient to adequatelyidentify a person at the time of the meeting. Likewise, some servicesshow a GPS location of a contractor on a map of an application. However,GPS doesn't work inside a building, and constantly updating a positiononly works with a strong internet connection.

As such, there is a need to securely determine that an interaction iswith the right stranger in a way that is restricted to physical locationand that works even without an internet connection or access to reliableGPS locations.

SUMMARY

In an embodiment, a system for verifying an identity of a user includesa first client electronic device associated with a first user, and acomputer-readable storage medium having one or more programminginstructions that, when executed, cause the first client electronicdevice to receive, from a provider electronic device, a first secret anda second secret, detect, by a receiver of the first client electronicdevice, a wireless signal being broadcast by a second client electronicdevice in proximity to a specified physical location where theinteraction is to occur, establish a communication channel with thesecond client electronic device, send the first secret to the secondclient electronic device via the communication channel, receive datafrom the second client electronic device via the communication channel,determine whether the received data matches the second secret, and inresponse to determining that the received data matches the secondsecret, cause an alert to be provided to the first user via the firstclient electronic device. The provider electronic device is associatedwith a service provider that has matched the first user and a seconduser for an interaction. The second client electronic device isassociated with the second user.

The system may identify a received signal strength indicator included inthe wireless signal, and determine whether the second client electronicdevice is within a threshold distance from the first client electronicdevice. The system may establish the communication channel with thesecond client electronic device in response to determining that thesecond client electronic device is within the threshold distance.

The system may receive input from the first user, and in response toreceiving input from the first user, cause the receiver to listen forthe wireless signal.

The system may detect the wireless signal being broadcast by the secondclient electronic device by receiving, from the provider electronicdevice, a notification that the second user is in proximity to thespecified physical location, and in response to receiving thenotification, cause the receiver to listen for the wireless signal.

The system may receive data from the second client electronic device viathe communication channel by receiving signed data, and obtaining thereceived data from the received signed data using a public keyassociated with the second client electronic device.

The system may sign the first secret using a private key associated withthe first client electronic device to generate a signed secret, and sendthe signed secret to the second client electronic device.

The system may include a second computer-readable storage medium havingone or more programming instructions that, when executed, cause thesecond client electronic device to receive the signed secret, obtain thefirst secret from the signed secret using a public key associated withthe first client electronic device, determine whether data received bythe second client electronic device from the service provider matchesthe first secret, and in response to determining that the data receivedby the second client electronic device from the service provider matchesthe first secret, cause an alert to be provided to the second user viathe second client electronic device.

The system may include a second computer-readable storage medium havingone or more programming instructions that, when executed, cause thesecond client electronic device to receive the first secret, determinewhether data received by the second client electronic device from theservice provider matches the first secret, and in response todetermining that the data received by the second client electronicdevice from the service provider matches the first secret, cause analert to be provided to the second user via the second client electronicdevice.

In an embodiment, a system for verifying an identity of a user includesa first client electronic device that is associated with a first user,and a computer-readable storage medium having one or more programminginstructions that, when executed, cause the first client electronicdevice to receive, from a provider electronic device, a first secret anda second secret, broadcast, by a transmitter of the first clientelectronic device, a signal unique to the first client electronic devicewhen the first client electronic device is in proximity to a specifiedphysical location where the interaction is to occur, detect a connectionthat a second client electronic device establishes with the first clientelectronic device, send the first secret to the second client electronicdevice, receive, by a receiver of the first client electronic device,data from the second client electronic device, determine whether thereceived data matches the second secret, and in response to determiningthat the received data matches the second secret, cause an alert to beprovided to the first user via the first client electronic device. Theprovider electronic device is associated with a service provider thathas matched the first user with a second user for an interaction. Thesecond client electronic device is associated with the second user.

The system may broadcast a signal unique to the first client electronicdevice when the first client electronic device is in proximity to aspecified physical location where the interaction is to occur bydetermining that the first client electronic device is in proximity tothe specified physical location, and in response to determining that thefirst client electronic device is in proximity to the specified physicallocation, automatically broadcasting the signal.

The system may broadcast a signal unique to the first client electronicdevice when the first client electronic device is in proximity to aspecified physical location where the interaction is to occur byreceiving input from the first user, and in response to receiving inputfrom the first user, automatically broadcasting the signal.

The signal may include a received signal strength indicator associatedwith the first client electronic device.

The system may receive data from the second client electronic device byreceiving signed data, and obtaining the received data from the receivedsigned data using a public key associated with the second clientelectronic device.

The system may sign the first secret using a private key associated withthe first client electronic device to generate a signed secret, and sendthe signed secret to the second client electronic device.

The system may include a second computer-readable storage medium havingone or more programming instructions that, when executed, cause thesecond client electronic device to receive the signed secret, obtain thefirst secret from the signed secret using a public key associated withthe first client electronic device, determine whether data received bythe second electronic device from the service provider matches the firstsecret, and in response to determining that the data received by thesecond electronic device from the service provider matches the firstsecret, cause an alert to be provided to the second user via the secondclient electronic device.

In an embodiment, a system for verifying an identity of a user includesa first client electronic device associated with a first user, and acomputer-readable storage medium having one or more programminginstructions that, when executed, cause the first client electronicdevice to detect, by a receiver of the first client electronic device, awireless signal being broadcast by a second client electronic device inproximity to a specified physical location where an interaction is tooccur, detect a received signal strength indicator from the detectedwireless signal, send the received signal strength indicator to aprovider electronic device associated with a service provider, receive anotification from the provider electronic device indicating that thefirst client electronic device is within a threshold distance from thesecond electronic device, and in response to receiving the notification,cause an alert to be provided to the first user via the first clientelectronic device. The second client electronic device is associatedwith the second user, and a service provider has matched the first userand the second user for the interaction.

The system may include a second computer-readable storage medium havingone or more programming instructions that, when executed, cause thesecond client electronic device to receive a second notification fromthe provider electronic device indicating that the first clientelectronic device is within the threshold distance from the secondclient electronic device, and in response to receiving the secondnotification, cause an alert to be provided to the second user via thesecond client electronic device.

In an embodiment, a system for verifying an identity of a user includesa provider electronic device, and a computer-readable storage mediumhaving one or more programming instructions that, when executed, causethe provider electronic device to receive from a first client electronicdevice, a received signal strength indicator indicating a proximity ofthe first client electronic device to a second client electronic devicein proximity to a specified physical location, compare the receivedsignal strength indicator to a threshold distance value to determinewhether the first client electronic device and the second clientelectronic device are within the threshold distance from one another,and in response to determining that the first client electronic deviceand the second client electronic device are within the thresholddistance from one another, send a notification to the first clientelectronic device, the second client electronic device, or both thefirst client electronic device and the second client electronic device.The first client electronic device is associated with a first user. Thesecond client electronic device is associated with a second user. Aservice provider associated with the provider electronic device hasmatched the first user and the second user for an interaction at thespecified physical location.

The system may include a second computer-readable storage medium havingone or more programming instructions that, when executed, cause thefirst client electronic device to receive the notification, and cause analert to be provided to the first user via the first client electronicdevice.

The system may include a second computer-readable storage medium havingone or more programming instructions that, when executed, cause thesecond client electronic device to receive the notification, and causean alert to be provided to the second user via the second clientelectronic device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system for securing data according to anembodiment.

FIG. 2A illustrates a flow chart of an example method of identifying auser according to an embodiment.

FIG. 2B illustrates a flow chart of an example method of identifying auser according to an embodiment.

FIG. 3A illustrates a flow chart of an example method of identifying auser according to an embodiment.

FIG. 3B illustrates a flow chart of an example method of identifying auser according to an embodiment.

FIG. 4 illustrates a block diagram of example hardware that may be usedto contain or implement program instructions according to an embodiment.

DETAILED DESCRIPTION

This disclosure is not limited to the particular systems, methodologiesor protocols described, as these may vary. The terminology used in thisdescription is for the purpose of describing the particular versions orembodiments only, and is not intended to limit the scope.

As used in this document, the singular forms “a,” “an,” and “the”include plural reference unless the context clearly dictates otherwise.Unless defined otherwise, all technical and scientific terms used hereinhave the same meanings as commonly understood by one of ordinary skillin the art. All publications mentioned in this document are incorporatedby reference. All sizes recited in this document are by way of exampleonly, and the invention is not limited to structures having the specificsizes or dimension recited below. As used herein, the term “comprising”means “including, but not limited to.”

The following terms shall have, for purposes of this application, therespective meanings set forth below:

A “computing device” or “electronic device” refers to a device thatincludes a processor and non-transitory, computer-readable memory. Thememory may contain programming instructions that, when executed by theprocessor, cause the computing device to perform one or more operationsaccording to the programming instructions. As used in this description,a “computing device” or “electronic device” may be a single device, orany number of devices having one or more processors that communicatewith each other and share data and/or instructions. Examples ofcomputing devices or electronic devices include, without limitation,personal computers, servers, mainframes, gaming systems, televisions,and portable electronic devices such as smartphones, personal digitalassistants, cameras, tablet computers, laptop computers, media players,wearable devices and the like. Various elements of an example of acomputing device or processor are described below in reference to FIG.4.

The terms “memory,” “computer-readable medium” and “data store” eachrefer to a non-transitory device on which computer-readable data,programming instructions or both are stored. Unless the contextspecifically states that a single device is required or that multipledevices are required, the terms “memory,” “computer-readable medium” and“data store” include both the singular and plural embodiments, as wellas portions of such devices such as memory sectors.

A “secret” refers to data that is to be protected and shared only withauthorized parties. For instance, a secret may be information known onlyto parties of a communication so that any party's possession of the dataor a portion of the data can be used to authenticate a party's identity.Examples of secrets may include, without limitation, private encryptionkeys, private signing keys, bitcoin keys, passwords, biometrics, and/orthe like.

A “user account” refers to an account of a user with a provider, such asa service provider, through which the user can access or is providedwith access to software, services and/or the like. A user account may beaccessed via one or more authentication credentials such as a login, apassword, a biometric, a security token and/or the like.

The present disclosure relates generally to identify verificationauthentication systems. Specifically, this disclosure describes methodsand systems that allow a user to meet or interact with a stranger wheresuch interaction is mediated through a centralized platform. As used inthis disclosure, a stranger refers to an individual whose identity is tobe verified by another. In various embodiments, a stranger may beanother system user, a service representative, and/or the like.

In certain situations, for example food delivery, a stranger may besomeone who is unknown to a user. In other situations, a user may havesome information about a stranger's identity such as, for example, apicture, a physical description, a name, a license plate, and/or thelike. For instance, a user and a stranger may both be online datingservice subscribers who are matched for a date, and have profileinformation and one or more pictures of the other. In other situations,a user may have other familiarity or acquaintance with a stranger, butmay still have a desire to verify his or her identity.

In various embodiments, a user may have a user account with one or moreproviders. A user may use a user account to access software, servicesand/or the like of the provider. Example user accounts may include,without limitation, an online dating service account, a foodordering/delivery service account, a ride sharing account, a contractingservice account, a child care service account, an online marketplaceaccount, and/or the like.

A user may access his or her account via an application installed on aclient electronic device of the user. A “client electronic device” or“client device” refers to an electronic device associated with a user,such as, for example, a smartphone, a tablet, a wearable device and/orthe like.

In various embodiments, a stranger interaction may be between a user(Stranger 1) and a representative of a provider (Stranger 2). Forexample, a user may be a customer, and a representative may be a driverworking on behalf of a ride sharing service provider. As anotherexample, a user may be a customer, and a representative may be adelivery person working on behalf of an ordering/delivery service.Additional and/or alternate types of roles, responsibilities and/orrelationships are contemplated within the disclosure.

In other embodiments, a stranger interaction may occur between two usersof a provider. For instance, a provider may match two of its users for aparticular purpose. For instance, an online dating service may match twoof its users (Stranger 1 and Stranger 2) for a date. As another example,a provider may match two users to buy, sell or trade merchandise.

FIG. 1 illustrates an example system for confirming the identity of astranger according to an embodiment. As illustrated by FIG. 1, thesystem 100 may include a first client electronic device 102, a secondclient electronic device 104, and one or more provider electronicdevices 106. The first client electronic device 102 may be associatedwith a first stranger, and a second client electronic device 104 may beassociated with a second stranger. The first client electronic device102 and/or the second electronic device 104 may be in communication withthe provider electronic device(s) 106 via a communication network 108.

In an embodiment, a provider electronic device 106 may be an electronicdevice associated with a provider that is responsible for facilitating astranger interaction, such as, for example, an online dating service, aride sharing service, an online marketplace and/or the like. Forinstance, as illustrated in FIG. 1, one or more provider electronicdevices 106 may be part of a central platform 112 associated with aservice provider. A central platform 112 may include one or more datastores that may store information pertinent to the service and/orarranged interactions.

Examples of a provider electronic device 106 may include withoutlimitation, a laptop computer, a desktop computer, a tablet, a mobiledevice, a server, a mainframe or other computing or electronic device.

A communication network 108 may be a local area network (LAN), a widearea network (WAN), a mobile or cellular communication network, anextranet, an intranet, the Internet, a short range communication networkand/or the like. Although FIG. 1 shows a single communication network108 it is to be understood that the network may be implemented asmultiple communication networks.

In various embodiments, a first client electronic device 102 maycommunicate with a second client electronic device 104, and vice versa,via a communication network 110. Although FIG. 1 shows two clientelectronic devices 102, 104 in communication, it is understood thatadditional and/or alternate client electronic devices may be used withinthe scope of this disclosure.

In various embodiments, a first client electronic device 102 and asecond client electronic device 104 may communicate with one another viashort range communication such as, for example, near field communication(NFC), radio frequency identification (RFID), Bluetooth and/or the like.One or more client electronic devices 102, 104 may include a short rangecommunication receiver 114, 116 and/or transmitter 118, 120 such as, anRFID tag, a Bluetooth antenna, an NFC chip and/or the like. In certainembodiments, a client electronic device 102, 104 may communicate withone or more other client electronic devices 102, 104 via a communicationnetwork 110, which may be an authenticated and secure communicationchannel.

FIG. 2A illustrates an example method of identifying a user according toan embodiment. As illustrated, in FIG. 2A, a first user (User 1) mayinstall 200 an application on User 1's client electronic device (ClientDevice 1). For example, User 1 may download and install 200 anapplication associated with a central platform of a service provider.

User 1 may be a subscriber, customer, client or other end user of aservice associated with the central platform and/or service provider. Acentral platform may include one or more provider electronic devicesthat may host software and/or services associated with the installedapplication.

Once installed, Client Device 1 may generate 202 a strong public privatekey pair (PK1, SK1) associated with User 1. For instance, Client Device1 may generate 202 a 256-bit public key and a 256-bit private keyaccording to an embodiment. It is understood that other types of privateand public keys may be used within the scope of this disclosure.

Client Device 1 may store 204 the private and public keys to a datastore such as, for example, operation system storage of Client Device 1.In various embodiments, User 1 may create 206 an account with a centralplatform. As part of the creation, the central platform may generate aunique identifier associated with User 1, Client Device 1 and/or thelike. In an embodiment, Client Device 1 may send 208 its public key tothe central platform. The central platform may store the received publickey such that it is associated with the unique identifier of User 1and/or Client Device 1.

As illustrated by FIG. 2A, a User 2 may install 210 an application onhis or her client electronic device (Client Device 2). In an embodiment,User 2 may be a subscriber, customer, client or other end user of aservice associated with the central platform and/or service provider. Inanother embodiment, User 2 may be a contractor or other representativeof the service provider such as, for example, a ride-share driver, adelivery person, a contractor and/or the like.

The application that User 2 installs 210 may be the same or similarapplication that User 1 installs. Alternatively, User 2 may install 210an application that is different from the one that User 1 installs, butthat corresponds to the central platform. Client Device 2 may generate212 a strong public private key pair (PK2, SK2) associated with User 2.For instance, Client Device 2 may generate 212 a 256-bit public key anda 256-bit private key according to an embodiment. It is understood thatother types of private and public keys may be used within the scope ofthis disclosure.

Client Device 2 may store 214 the private and public keys to a datastore such as, for example, operation system storage. In variousembodiments, User 2 may create 216 an account with a central platform.As part of the creation, the central platform may generate a uniqueidentifier associated with User 2, Client Device 2 and/or the like. Inan embodiment, Client Device 2 may send 218 its public key to thecentral platform. The central platform may store the received public keysuch that it is associated with the unique identifier of User 2 and/orClient Device 2.

As shown in FIG. 2A, the central platform may match 220 User 1 and User2 for a transaction or interaction. For example, the central platformmay match 220 User 1 and User 2 in response to User 1 requesting atransaction or interaction be arranged by the central platform with astranger at a specified location.

For instance, if the central platform is associated with a ride-sharingcompany, the central platform may match a rider (User 1) with a driver(User 2). As another example, if the central platform is associated witha dating service, the central platform may match a first user (User 1)with a second user (User 2). As yet another example, if the centralplatform is associated with a home repair service, the central platformmay match a resident (e.g., a home owner, renter, etc.) (User 1) with arepair technician (User 2). Additional and/or alternate relationshipsand/or matches may be used within the scope of this disclosure.

Once a match is made, the central platform may generate 222 one or moresecret values. For example, the central platform may generate 222 afirst secret (S1), and a second secret (S2). The secret values may bedifferent from one another, or they may be the same. The secret valuesmay be valid for the interaction between User 1 and User 2 only. Invarious embodiments, the secret values may be randomly orpseudo-randomly generated values.

The central platform may send 224 the two secret values (S1, S2) toClient Device 1. Optionally, the central platform may also send 226 thepublic key associated with Client Device 2 and/or User 2 (PK2) to ClientDevice 1. Similarly, the central platform may send 228 the two secretvalues (S1, S2) to Client Device 2. Optionally the central platform mayalso send 230 the public key associated with Client Device 1 and/or User1 (PK1) to Client Device 2.

In various embodiments, the meeting or interaction that is arrangedbetween User 1 and User 2 may be arranged for a particular time andplace. The place may be a specified physical location where User 1 andUser 2 are to meet. For instance, if the interaction is a delivery, thespecified physical location for the interaction may be User 1'sapartment, home or other address. As another example, if the interactionis a ride-share, the specified physical location for the interaction maybe a pickup location that User 1 specifies. In various embodiments, thetime and specified physical location for an interaction may be mediatedby the central platform.

User 1 may arrive (or be present) at the specified physical locationwith Client Device 1 at or around the time specified for theinteraction. User 2 may arrive at the specified physical location withClient Device 2 at or around the time specified for the interaction.

Client Device 2 may broadcast 232 a wireless signal over a wirelesschannel. For example, Client Device 2 may broadcast 232 a wirelesssignal over a wireless channel when User 2 arrives at the specifiedphysical location. In an embodiment, a short range communicationtransmitter of Client Device 2 may broadcast 232 a wireless signal. Thewireless signal may be unique to Client Device 2, and may indicate thatUser 2 has arrived at the specified physical location. In variousembodiments, the wireless signal may be encrypted.

Client Device 2 may automatically begin broadcasting 232 a wirelesssignal when Client Device 2 is at or in proximity to the specifiedphysical location. For instance, Client Device 2 may use GPS or othergeolocation technology to determine Client Device 2's position. If sucha position is at or within a certain proximity to the specified physicallocation, Client Device 2 may automatically begin broadcasting 232 awireless signal.

As another example, Client Device 2 may begin broadcasting 232 awireless signal in response to receiving input from User 2. Forinstance, User 2 may press a button, provide a verbal command orotherwise provide input to the application indicating that User 2 hasarrived at the specified physical location.

In various embodiments, Client Device 1 may listen 234 for the wirelesssignal being broadcast by Client Device 2 at the specified physicallocation. For example, a short range communication receiver may listen234 for the wireless signal. In various embodiments, Client Device 1 mayautomatically begin listening 234 for a wireless signal when ClientDevice 1 is at or in proximity to the specified physical location. Forinstance, Client Device 1 may use GPS or other geolocation technology todetermine Client Device 1's position. If such a position is at or withina certain proximity to the specified physical location, Client Device 1may automatically begin listening 234 a wireless signal.

In another embodiment, Client Device 1 may begin listening 234 for awireless signal in response to receiving input from User 1. Forinstance, User 1 may press a button, provide a verbal command orotherwise provide input to the application when User 1 knows or suspectsthat User 2 has arrived at the specified physical location. Forinstance, in a delivery scenario, User 1 may press a button on ClientDevice 1 when User 2 knocks on User 1's door.

In another embodiment, Client Device 1 may begin listening 234 for awireless signal in response to receiving a notification that User 2 isat the specified physical location. For instance, the central platformmay send a notification to Client Device 1 when Client Device 2 arrivesat the specified physical location. For instance, the central platformmay determine, via GPS or other geolocation technology, that ClientDevice 2 is at or near the specified physical location. In response, thecentral platform may send a notification to Client Device 1, which maycause Client Device 1 to begin listening 234 for the wireless signalbeing broadcast by Client Device 2.

Client Device 1 may detect 236 Client Device 2's wireless signal. In anembodiment, if the broadcast wireless signal is encrypted, Client Device1 may decrypt the encrypted wireless signal. The wireless signal beingbroadcast by Client Device 2 may include or be derived from somecombination of S1, S2, PK1 and/or PK2. As such, Client Device 1 maydetect the correct wireless signal by determining whether the signalincludes or is derived from S1, S2, PK1 and/or PK2.

In various embodiments, Client Device 1 may determine 238 whether ClientDevice 2 is in close physical proximity to Client Device 1. In variousembodiments, close physical proximity may be within a certain thresholddistance, for example, two to four feet. Alternate distances may be usedwithin the scope of this disclosure. For instance, Client Device 1 maydetect a received signal strength indicator (RSSI) from the wirelesssignal being broadcast by Client Device 2. Based, on the RSSI, ClientDevice 1 may determine whether Client Device 1 is within a thresholddistance from Client Device 2.

In response to determining that Client Device 2 is in close physicalproximity to Client Device 1, Client Device 1 may establish 240 aconnection to Client Device 2 over a wireless channel. In otherembodiments, Client Device 1 may not determine a proximity to ClientDevice 2, but instead may establish 240 a connection to Client Device 2when Client Device 1 detects Client Device 2's broadcast signal.

Client Device 1 may send 242 one of the secrets (e.g., S1) to ClientDevice 2 over the wireless channel. In various embodiments, ClientDevice 1 may sign the secret to generate a cryptographic signature, andmay send the cryptographic signature to Client Device 2. For example,Client Device 1 may sign the secret with Client Device 1's private key(SK1) to create a cryptographic signature.

Client Device 2 may receive 244 the secret (or cryptographic signature)via the wireless channel. If Client Device 2 receives 244 acryptographic signature, it may verify the cryptographic signature tomatch the secret. For example, Client Device 2 may obtain Client Device1's public key (PK1) from the central platform, and may use it to verifythe cryptographic signature.

Client Device 2 may verify 246 that the received secret matches a secretreceived from the central platform in step 228. In response to verifying246 that the received secret matches a secret provided by the centralplatform, Client Device 2 may send 248 the other secret (e.g., S2) toClient Device 1. In various embodiments, Client Device 2 may sign thesecret to generate a cryptographic signature, and may send thecryptographic signature to Client Device 1. For example, Client Device 2may sign the secret with Client Device 2's private key (SK2) to create acryptographic signature.

Client Device 1 may receive 250 the secret (or cryptographic signature)via the wireless channel. If Client Device 1 receives a cryptographicsignature, it may verify the cryptographic signature to match thesecret. For example, Client Device 1 may obtain Client Device 2's publickey (PK2) from the central platform, and may use it to verify thecryptographic signature.

Client Device 1 may verify 252 that the received secret matches a secretreceived from the central platform in step 224. In response to verifying252 that the received secret matches the secret from the centralplatform, Client Device 1 may disconnect 254 the connection betweenClient Device 1 and Client Device 2 over the wireless channel.

In response to Client Device 1 verifying 252 that the received secretmatches a secret received from the central platform, Client Device 1 maycause 256 an alert to be provided to User 1 via Client Device 1. Thealert may be an indication that User 2 has been verified and is in closephysical proximity to User 1 at their specified physical location Forinstance, Client Device 1 may cause 256 a visual alert or notification(e.g., an alert window) to be displayed to User 1. As another example,Client Device 1 may vibrate a certain number of times. As yet anotherexample, Client Device 1 may generate an audio alert (e.g., a beep,chime or other audio indication).

In response to Client Device 2 verifying 246 that the secret it receivedfrom Client Device 1 matches a secret received from the centralplatform, Client Device 2 may cause 258 an alert to be provided to User2 via Client Device 2. The alert may be an indication that User 1 hasbeen verified and is in close physical proximity to User 2 at theirspecified physical location. For instance, Client Device 2 may cause 258a visual alert or notification (e.g., an alert window) to be displayedto User 2. As another example, Client Device 2 may vibrate a certainnumber of times. As yet another example, Client Device 2 may generate anaudio alert (e.g., a beep, chime or other audio indication).

FIG. 2B illustrates another example method of identifying a useraccording to an embodiment. As illustrated, in FIG. 2B, the method shownmay be the same as that illustrated in FIG. 2A from steps 200-230.

However, in this embodiment, Client Device 1 may broadcast 235 awireless signal over a wireless channel. For example, Client Device 1may broadcast 235 a wireless signal over a wireless channel when User 1arrives at the specified location. For example, a short rangecommunication transmitter of Client Device 1 may broadcast 235 awireless signal. The wireless signal may be unique to Client Device 1,and may indicate that User 1 has arrived at the specified physicallocation. In various embodiments, the wireless signal may be encrypted.

Client Device 1 may automatically begin broadcasting 235 a wirelesssignal when Client Device 1 is at or in proximity to the specifiedphysical location. For instance, Client Device 1 may use GPS or othergeolocation technology to determine Client Device 1's position. If sucha position is at or within a certain proximity to the specified physicallocation, Client Device 1 may automatically begin broadcasting 235 awireless signal.

As another example, Client Device 1 may begin broadcasting 235 awireless signal in response to receiving input from User 1. Forinstance, User 1 may press a button, provide a verbal command orotherwise provide input to the application indicating that User 1 hasarrived at the specified physical location.

In various embodiments, Client Device 2 may listen 237 for the wirelesssignal being broadcast by Client Device 1 at the specified physicallocation. For example, a short range communication receiver may listen237 for the wireless signal. In various embodiments, Client Device 2 mayautomatically begin listening 237 for a wireless signal when ClientDevice 2 is at or in proximity to the specified physical location. Forinstance, Client Device 2 may use GPS or other geolocation technology todetermine Client Device 2's position. If such a position is at or withina certain proximity to the specified physical location, Client Device 2may automatically begin listening 237 a wireless signal.

In another embodiment, Client Device 2 may begin listening 237 for awireless signal in response to receiving input from User 2. Forinstance, User 2 may press a button, provide a verbal command orotherwise provide input to the application when User 2 knows or suspectsthat User 1 has arrived at the specified physical location. Forinstance, in a delivery scenario, User 2 may press a button on ClientDevice 2 when User 1 knocks on User 2's door.

In another embodiment, Client Device 2 may begin listening 237 for awireless signal in response to receiving a notification that User 1 isat the specified physical location. For instance, the central platformmay send a notification to Client Device 2 when Client Device 1 arrivesat the specified physical location. For instance, the central platformmay determine, via GPS or other geolocation technology that ClientDevice 1 is at or near the specified physical location. In response, thecentral platform may send a notification to Client Device 2, which maycause Client Device 2 to begin listening 237 for the wireless signalbeing broadcast by Client Device 1.

Client Device 2 may detect 239 Client Device 1's wireless signal. In anembodiment, if the broadcast wireless signal is encrypted, Client Device2 may decrypt the encrypted wireless signal. The wireless signal beingbroadcast by Client Device 1 may include or be derived from somecombination of S1, S2, PK1 and/or PK2. As such, Client Device 2 maydetect the correct wireless signal by determining whether the signalincludes or is derived from S1, S2, PK1 and/or PK2.

In various embodiments, Client Device 2 may determine 241 whether ClientDevice 1 is in close physical proximity to Client Device 2. In variousembodiments, close physical proximity may be within a certain thresholddistance, for example, two to four feet. Alternate distances may be usedwithin the scope of this disclosure. For instance, Client Device 2 maydetect a received signal strength indicator (RSSI) from the wirelesssignal being broadcast by Client Device 1. Based, on the RSSI, ClientDevice 2 may determine whether Client Device 2 is within a thresholddistance from Client Device 1.

In response to determining that Client Device 1 is in close physicalproximity to Client Device 2, Client Device 2 may establish 243 aconnection to Client Device 1 over a wireless channel. In otherembodiments, Client Device 2 may not determine a proximity to ClientDevice 1, but instead may establish 243 a connection to Client Device 1when Client Device 2 detects Client Device 1's broadcast signal.

Client Device 2 may send 245 one of the secrets (e.g., S2) to ClientDevice 1 over the wireless channel. In various embodiments, ClientDevice 2 may sign the secret to generate a cryptographic signature, andmay send the cryptographic signature to Client Device 1. For example,Client Device 2 may sign the secret with Client Device 2's private key(SK2) to create a cryptographic signature.

Client Device 1 may receive 247 the secret (or cryptographic signature)via the wireless channel. If Client Device 1 receives 247 acryptographic signature, it may verify the cryptographic signature tomatch the secret. For example, Client Device 1 may obtain Client Device2's public key (PK2) from the central platform, and may use it to verifythe cryptographic signature.

Client Device 1 may verify 249 that the received secret matches a secretreceived from the central platform in step 224. In response to verifying249 that the received secret matches a secret provided by the centralplatform, Client Device 1 may send 251 the other secret (e.g., S1) toClient Device 2. In various embodiments, Client Device 1 may sign thesecret to generate a cryptographic signature, and may send 251 thecryptographic signature to Client Device 2. For example, Client Device 1may sign the secret with Client Device 1's private key (SK1) to create acryptographic signature.

Client Device 2 may receive 253 the secret (or cryptographic signature)via the wireless channel. If Client Device 2 receives 253 acryptographic signature, it may verify the cryptographic signature tomatch the secret. For example, Client Device 2 may obtain Client Device1's public key (PK1) from the central platform, and may use it to verifythe cryptographic signature.

Client Device 2 may verify 255 that the received secret matches a secretreceived from the central platform in step 228. In response to verifying255 that the received secret matches the secret from the centralplatform, Client Device 2 may disconnect 257 the connection betweenClient Device 2 and Client Device 1 over the wireless channel.

In response to Client Device 2 verifying 255 that the received secretmatches a secret received from the central platform, Client Device 2 maycause 259 an alert to be provided to User 2 via Client Device 2. Thealert may be an indication that User 1 has been verified and is in closephysical proximity to User 2 at their specified physical location Forinstance, Client Device 2 may cause 259 a visual alert or notification(e.g., an alert window) to be displayed to User 2. As another example,Client Device 2 may vibrate a certain number of times. As yet anotherexample, Client Device 2 may generate an audio alert (e.g., a beep,chime or other audio indication).

In response to Client Device 1 verifying 249 that the secret it receivedfrom Client Device 2 matches a secret received from the centralplatform, Client Device 1 may cause 261 an alert to be provided to User1 via Client Device 1. The alert may be an indication that User 2 hasbeen verified and is in close physical proximity to User 1 at theirspecified physical location. For instance, Client Device 1 may cause 261a visual alert or notification (e.g., an alert window) to be displayedto User 1. As another example, Client Device 1 may vibrate a certainnumber of times. As yet another example, Client Device 1 may generate anaudio alert (e.g., a beep, chime or other audio indication).

FIG. 3A illustrates an example system for confirming the identity of auser according to an embodiment. As illustrated, in FIG. 3A, a firstuser (User 1) may install 300 an application on User 1's clientelectronic device (Client Device 1). For example, User 1 may downloadand install 300 an application associated with a central platform of aservice provider.

User 1 may be a subscriber, customer, client or other end user of aservice associated with the central platform and/or service provider. Acentral platform may include one or more provider electronic devicesthat may host software and/or services associated with the installedapplication.

In various embodiments, User 1 may create 302 an account with a centralplatform. As part of the creation, the central platform may generate aunique identifier associated with User 1, Client Device 1 and/or thelike.

As illustrated by FIG. 3A, a User 2 may install 304 an application onhis or her client electronic device (Client Device 2). In an embodiment,User 2 may be a subscriber, customer, client or other end user of aservice associated with the central platform and/or service provider. Inanother embodiment, User 2 may be a contractor or other representativeof the service provider such as, for example, a ride-share driver, adelivery person, a contractor and/or the like.

The application that User 2 installs 304 may be the same or similarapplication that User 1 installs. Alternatively, User 2 may install 304an application that is different from the one that User 1 installs, butthat corresponds to the central platform.

In various embodiments, User 2 may create 306 an account with a centralplatform. As part of the creation, the central platform may generate aunique identifier associated with User 2, Client Device 2 and/or thelike.

As shown in FIG. 3A, the central platform may match 308 User 1 and User2 for a transaction or interaction. For example, the central platformmay match 308 User 1 and User 2 in response to User 1 requesting atransaction or interaction be arranged by the central platform with astranger at a specified location.

For instance, if the central platform is associated with a ride-sharingcompany, the central platform may match a rider (User 1) with a driver(User 2). As another example, if the central platform is associated witha dating service, the central platform may match a first user (User 1)with a second user (User 2). As yet another example, if the centralplatform is associated with a home repair service, the central platformmay match a resident (e.g., a home owner, renter, etc.) (User 1) with arepair technician (User 2). Additional and/or alternate relationshipsand/or matches may be used within the scope of this disclosure.

In various embodiments, the meeting or interaction that is arrangedbetween User 1 and User 2 may be arranged for a particular time andplace. The place may be a specified physical location where User 1 andUser 2 are to meet. For instance, if the interaction is a delivery, thespecified physical location for the interaction may be User 1'sapartment, home or other address. As another example, if the interactionis a ride-share, the specified physical location for the interaction maybe a pickup location that User 1 specifies. In various embodiments, thetime and specified physical location for an interaction may be mediatedby the central platform.

User 1 may arrive (or be present) at the specified physical locationwith Client Device 1 at or around the time specified for theinteraction. User 2 may arrive at the specified physical location withClient Device 2 at or around the time specified for the interaction.

Client Device 2 may broadcast 310 a wireless signal over a wirelesschannel. For instance, Client Device 2 may broadcast 310 a wirelesssignal over a wireless channel when User 2 arrives at the specifiedphysical location. A short range communication transmitter of ClientDevice 2 may broadcast 310 a wireless signal. The wireless signal may beunique to Client Device 2, and may indicate that User 2 has arrived atthe specified physical location. In various embodiments, the wirelesssignal may be encrypted.

Client Device 2 may automatically begin broadcasting 310 a wirelesssignal when Client Device 2 is at or in proximity to the specifiedphysical location. For instance, Client Device 2 may use GPS or othergeolocation technology to determine Client Device 2's position. If sucha position is at or within a certain proximity to the specified physicallocation, Client Device 2 may automatically begin broadcasting 310 awireless signal.

As another example, Client Device 2 may begin broadcasting 310 awireless signal in response to receiving input from User 2. Forinstance, User 2 may press a button, provide a verbal command orotherwise provide input to the application indicating that User 2 hasarrived at the specified physical location.

In various embodiments, Client Device 1 may listen 312 for the wirelesssignal being broadcast by Client Device 2 at the specified physicallocation. For example, a short range communication receiver may listen312 for the wireless signal. In various embodiments, Client Device 1 mayautomatically begin listening 312 for a wireless signal when ClientDevice 1 is at or in proximity to the specified physical location. Forinstance, Client Device 1 may use GPS or other geolocation technology todetermine Client Device 1's position. If such a position is at or withina certain proximity to the specified physical location, Client Device 1may automatically begin listening 312 a wireless signal.

In another embodiment, Client Device 1 may begin listening 312 for awireless signal in response to receiving input from User 1. Forinstance, User 1 may press a button, provide a verbal command orotherwise provide input to the application when User 1 knows or suspectsthat User 2 has arrived at the specified physical location. Forinstance, in a delivery scenario, User 1 may press a button on ClientDevice 1 when User 2 knocks on User 1's door.

In another embodiment, Client Device 1 may begin listening 312 for awireless signal in response to receiving a notification that User 2 isat the specified physical location. For instance, the central platformmay send a notification to Client Device 1 when Client Device 2 arrivesat the specified physical location. For instance, the central platformmay determine, via GPS or other geolocation technology, that ClientDevice 2 is at or near the specified physical location. In response, thecentral platform may send a notification to Client Device 1, which maycause Client Device 1 to begin listening 312 for the wireless signalbeing broadcast by Client Device 2.

Client Device 1 may detect 314 Client Device 2's wireless signal. In anembodiment, if the broadcast wireless signal is encrypted, Client Device1 may decrypt the encrypted wireless signal. The wireless signal beingbroadcast by Client Device 2 may include or be derived from the uniqueuser identifiers created by the central platform as part of the accountcreation process, for example, as described with respect to steps 302and/or 306. In another embodiment, the wireless signal being broadcastby Client Device 2 may include or be derived from another identifierderived and/or randomly or pseudo-randomly generated by the centralplatform and shared with Client Device 1 and Client Device 2 as part ofthe arranged meeting or interaction. As such, Client Device 1 may detectthe correct wireless signal by determining whether the signal includesor is derived from the shared unique identifier as specified by thecentral platform.

In various embodiments, Client Device 1 may detect 316 a received signalstrength indicator (RSSI) from the wireless signal being broadcast byClient Device 2. The RSSI may be indicative of a proximity of ClientDevice 1 to Client Device 2. Client Device 1 may send 318 the RSSI tothe central platform. The central platform may determine 320 whether,based on the RSSI, Client Device 1 is within a threshold distance fromClient Device 2. If the central platform determines 320 that ClientDevice 1 is not within a threshold distance from Client Device 2, thecentral platform may send a notification to Client Device 1. ClientDevice 1 may continue to detect 316 RSSI and send 318 the RSSI to thecentral platform until the central platform determines 320 that ClientDevice 1 is within a threshold distance from Client Device 2.

If the central platform determines 320 that Client Device 1 and ClientDevice 2 are within a threshold distance from one another, the centralplatform may send 322 a notification to Client Device 1 and/or to ClientDevice 2. The notification may cause Client Device 1 and/or ClientDevice 2 to generate 324 an alert to be provided to User 1 and User 2,respectively. The alert may be an indication that User 1 and User 2 havebeen verified and are in close physical proximity to one another attheir specified physical location. For instance, Client Device 1 and/orClient Device 2 may cause 324 a visual alert or notification (e.g., analert window) to be displayed to its user. As another example, ClientDevice 1 and/or Client Device 2 may vibrate a certain number of times.As yet another example, Client Device 1 and/or Client Device 2 maygenerate an audio alert (e.g., a beep, chime or other audio indication).

As illustrated, in FIG. 3B, the method shown may be the same as thatillustrated in FIG. 3A from steps 300-310.

However, in this embodiment, Client Device 1 may broadcast 315 awireless signal over a wireless channel. For example, Client Device 1may broadcast 315 a wireless signal over a wireless channel when User 1arrives at the specified location. For example, a short rangecommunication transmitter of Client Device 1 may broadcast 315 awireless signal. The wireless signal may be unique to Client Device 1,and may indicate that User 1 has arrived at the specified physicallocation. In various embodiments, the wireless signal may be encrypted.

Client Device 1 may automatically begin broadcasting 315 a wirelesssignal when Client Device 1 is at or in proximity to the specifiedphysical location. For instance, Client Device 1 may use GPS or othergeolocation technology to determine Client Device 1's position. If sucha position is at or within a certain proximity to the specified physicallocation, Client Device 1 may automatically begin broadcasting 315 awireless signal.

As another example, Client Device 1 may begin broadcasting 315 awireless signal in response to receiving input from User 1. Forinstance, User 1 may press a button, provide a verbal command orotherwise provide input to the application indicating that User 1 hasarrived at the specified physical location.

In various embodiments, Client Device 2 may listen 317 for the wirelesssignal being broadcast by Client Device 1 at the specified physicallocation. For example, a short range communication receiver may listen317 for the wireless signal. In various embodiments, Client Device 2 mayautomatically begin listening 317 for a wireless signal when ClientDevice 2 is at or in proximity to the specified physical location. Forinstance, Client Device 2 may use GPS or other geolocation technology todetermine Client Device 2's position. If such a position is at or withina certain proximity to the specified physical location, Client Device 2may automatically begin listening 317 a wireless signal.

In another embodiment, Client Device 2 may begin listening 317 for awireless signal in response to receiving input from User 2. Forinstance, User 2 may press a button, provide a verbal command orotherwise provide input to the application when User 2 knows or suspectsthat User 1 has arrived at the specified physical location. Forinstance, in a delivery scenario, User 2 may press a button on ClientDevice 2 when User 1 knocks on User 2's door.

In another embodiment, Client Device 2 may begin listening 317 for awireless signal in response to receiving a notification that User 1 isat the specified physical location. For instance, the central platformmay send a notification to Client Device 2 when Client Device 1 arrivesat the specified physical location. For instance, the central platformmay determine, via GPS or other geolocation technology, that ClientDevice 1 is at or near the specified physical location. In response, thecentral platform may send a notification to Client Device 2, which maycause Client Device 2 to begin listening 317 for the wireless signalbeing broadcast by Client Device 1.

Client Device 2 may detect 319 Client Device 1's wireless signal. In anembodiment, if the broadcast wireless signal is encrypted, Client Device2 may decrypt the encrypted wireless signal. The wireless signal beingbroadcast by Client Device 1 may include or be derived from the uniqueuser identifiers created by the central platform in steps 302 and/or306. In another embodiment, the wireless signal being broadcast byClient Device 1 may include or be derived from another identifierderived and/or randomly or pseudo-randomly generated by the centralplatform and shared with Client Device 1 and Client Device 2 as part ofthe arranged meeting or interaction. As such, Client Device 2 may detect319 the correct wireless signal by determining whether the signalincludes or is derived from the shared unique identifier as specified bythe central platform.

In various embodiments, Client Device 2 may detect 321 a received signalstrength indicator (RSSI) from the wireless signal being broadcast byClient Device 1. The RSSI may be indicative of a proximity of ClientDevice 1 to Client Device 2. Client Device 2 may send 323 the RSSI tothe central platform. The central platform may determine 325 whether,based on the RSSI, Client Device 1 is within a threshold distance fromClient Device 2. If the central platform determines 323 that ClientDevice 1 is not within a threshold distance from Client Device 2, thecentral platform may send a notification to Client Device 2. ClientDevice 2 may continue to detect 321 RSSI and send 323 the RSSI to thecentral platform until the central platform determines 325 that ClientDevice 1 is within a threshold distance from Client Device 2.

If the central platform determines 325 that Client Device 1 and ClientDevice 2 are within a threshold distance from one another, the centralplatform may send 327 a notification to Client Device 1 and/or to ClientDevice 2. The notification may cause 329 Client Device 1 and/or ClientDevice 2 to generate an alert to be provided to User 1 and User 2,respectively. The alert may be an indication that User 1 and User 2 havebeen verified and are in close physical proximity to one another attheir specified physical location. For instance, Client Device 1 and/orClient Device 2 may cause 329 a visual alert or notification (e.g., analert window) to be displayed to its user. As another example, ClientDevice 1 and/or Client Device 2 may vibrate a certain number of times.As yet another example, Client Device 1 and/or Client Device 2 maygenerate an audio alert (e.g., a beep, chime or other audio indication).

FIG. 4 depicts a block diagram of an example of internal hardware thatmay be used to contain or implement program instructions, such as theprocess steps discussed above, according to embodiments. A bus 400serves as an information highway interconnecting the other illustratedcomponents of the hardware. CPU 405 represents one or more processors ofthe system, performing calculations and logic operations required toexecute a program. CPU 405, alone or in conjunction with one or more ofthe other elements disclosed in FIG. 4, is an example of a processingdevice, computing device or processor as such terms are used within thisdisclosure. Memory devices (or processor-readable storage media) 420 mayinclude, for example read only memory (ROM), random access memory (RAM),an external or internal disk drive, a hard drive, flash memory, a USBdrive or the like. As indicated previously, these various drives andcontrollers are optional devices.

Program instructions, software or interactive modules for providing theinterface and performing any querying or analysis associated with one ormore data sets may be stored in one or more memory devices 420.

An optional display interface 430 may permit information from the bus400 to be displayed on the display 435 in audio, visual, graphic oralphanumeric format. Communication with external devices, such as aprint device, may occur using various communication ports 440. Acommunication port 440 may be attached to a communications network, suchas the Internet or an intranet. In various embodiments, an optionaltransmitter and/or receiver may permit the sending and receiving ofinformation to and from other device, respectively.

The hardware may also include an interface 445 which allows for receiptof data from input devices such as a keyboard 450 or other input device455 such as a mouse, a joystick, a touch screen, a remote control, apointing device, a video input device and/or an audio input device.

It will be appreciated that the various above-disclosed and otherfeatures and functions, or alternatives thereof, may be desirablycombined into many other different systems or applications orcombinations of systems and applications. Also that various presentlyunforeseen or unanticipated alternatives, modifications, variations orimprovements therein may be subsequently made by those skilled in theart which are also intended to be encompassed by the following claims.

1-15. (canceled)
 16. A method of verifying an identity of a user, themethod comprising: by a first client electronic device associated with afirst user: detecting, by a receiver of the first client electronicdevice, a wireless signal being broadcast by a second client electronicdevice in proximity to a specified physical location where aninteraction is to occur, wherein: the second client electronic device isassociated with the second user, a service provider has matched thefirst user and the second user for the interaction; detecting a receivedsignal strength indicator from the detected wireless signal, sending thereceived signal strength indicator to a provider electronic deviceassociated with the service provider, receiving a notification from theprovider electronic device indicating that the first client electronicdevice is within a threshold distance from the second electronic device,and in response to receiving the notification, causing an alert to beprovided to the first user via the first client electronic device. 17.The method of claim 16, further comprising, by the second clientelectronic device: receiving a second notification from the providerelectronic device indicating that the first client electronic device iswithin the threshold distance from the second client electronic device;and in response to receiving the second notification, causing an alertto be provided to the second user via the second client electronicdevice.
 18. A method of verifying an identity of a user, the methodcomprising: receiving, by a provider electronic device from a firstclient electronic device, a received signal strength indicatorindicating a proximity of the first client electronic device to a secondclient electronic device in proximity to a specified physical location,wherein: the first client electronic device is associated with a firstuser, the second client electronic device is associated with the seconduser, a service provider associated with the provider electronic devicehas matched the first user and the second user for an interaction at thespecified physical location; comparing, by the provider electronicdevice, the received signal strength indicator to a threshold distancevalue to determine whether the first client electronic device and thesecond client electronic device are within the threshold distance fromone another; and in response to determining that the first clientelectronic device and the second client electronic device are within thethreshold distance from one another, sending, by the provider electronicdevice, a notification to the first client electronic device, the secondclient electronic device, or both the first client electronic device andthe second client electronic device.
 19. The method of claim 18, furthercomprising, by the first client electronic device, receiving thenotification and causing an alert to be provided to the first user viathe first client electronic device.
 20. The method of claim 18, furthercomprising, by the second client electronic device, receiving thenotification and causing an alert to be provided to the second user viathe second client electronic device. 21-35. (canceled)
 36. A system forverifying an identity of a user, the system comprising: a first clientelectronic device associated with a first user; and a computer-readablestorage medium comprising one or more programming instructions that,when executed, cause the first client electronic device to: detect, by areceiver of the first client electronic device, a wireless signal beingbroadcast by a second client electronic device in proximity to aspecified physical location where an interaction is to occur, whereinthe second client electronic device is associated with the second user,and a service provider has matched the first user and the second userfor the interaction, detect a received signal strength indicator fromthe detected wireless signal, send the received signal strengthindicator to a provider electronic device associated with the serviceprovider, receive a notification from the provider electronic deviceindicating that the first client electronic device is within a thresholddistance from the second electronic device, and in response to receivingthe notification, cause an alert to be provided to the first user viathe first client electronic device.
 37. The system of claim 36, furthercomprising, a second computer-readable storage medium comprising one ormore programming instructions that, when executed, cause the secondclient electronic device to: receive a second notification from theprovider electronic device indicating that the first client electronicdevice is within the threshold distance from the second clientelectronic device; and in response to receiving the second notification,cause an alert to be provided to the second user via the second clientelectronic device.
 38. A system for verifying an identity of a user, thesystem comprising: a provider electronic device; and a computer-readablestorage medium comprising one or more programming instructions that,when executed, cause the provider electronic device to: receive from afirst client electronic device, a received signal strength indicatorindicating a proximity of the first client electronic device to a secondclient electronic device in proximity to a specified physical location,wherein: the first client electronic device is associated with a firstuser, the second client electronic device is associated with the seconduser, a service provider associated with the provider electronic devicehas matched the first user and the second user for an interaction at thespecified physical location, compare the received signal strengthindicator to a threshold distance value to determine whether the firstclient electronic device and the second client electronic device arewithin the threshold distance from one another, and in response todetermining that the first client electronic device and the secondclient electronic device are within the threshold distance from oneanother, send a notification to the first client electronic device, thesecond client electronic device, or both the first client electronicdevice and the second client electronic device.
 39. The system of claim38, further comprising, a second computer-readable storage mediumcomprising one or more programming instructions that, when executed,cause the first client electronic device to: receive the notification;and cause an alert to be provided to the first user via the first clientelectronic device.
 40. The system of claim 38, further comprising, asecond computer-readable storage medium comprising one or moreprogramming instructions that, when executed, cause the second clientelectronic device to: receive the notification; and cause an alert to beprovided to the second user via the second client electronic device.